ObjectDB ObjectDB

Internal Website Search

71-80 of 200 resultsRefresh
18

How do I achieve a Deep Fetch using JOIN FETCH?

that I can express one level of eager fetch in JPQL as follows: SELECT c FROM C JOIN FETCH c.bList WHERE c.id=:id But when I attempt to take it to the 2nd level: SELECT c FROM C JOIN FETCH c.bList JOIN FETCH c.bList.aList WHERE c.id=:id I get an error along the lines of: Invalid fetch path
18

Lazy Init / Eager / Join Fetch collection strategy ? What to choose ?

,join fetch seems to be the right choice. What about ObjectDb ? The implementation is totally different. Is an "All eager strategy" more efficient that many join fetch ( cartesian product + distinct ... all strategy" Or "Fetch Join strategy" for ObjectDb ? Regards, Xirt xirt Sylvain > Is an "All eager
4

javax.persistence.criteria.Fetch

javax.persistence.criteria Interface Fetch<Z,X> Superinterfaces: FetchParent<Z,X> Represents a join ... a fetch join to the specified attribute using an inner join. Create a fetch join to the specified attribute using an inner join. Parameters: attributeName - name of the attribute for the target
4

javax.persistence.criteria.CriteriaQuery

removed, and results will be returned in no particular order. The left-to-right sequence of the ordering ... when it results from a get or join operation and the query result type is specified. For example ... (Product.class); q2.select(q2.from(Order.class) .join("items
4

Issue with DISTINCT Select

.foundation.contact.individual.IndividualContact $1 LEFT JOIN $1.profile $2 WHERE ((TYPE($1)=class com ... using the left join to select all entities, also those which have profile = null quasado Alexander Adam ... is invalid: SELECT DISTINCT $1 FROM IndividualContact $1 LEFT JOIN $1.profile $2 ORDER BY UPPER($2
4

JoinType.RIGHT

Enum Constant javax.persistence.criteria.JoinType RIGHT Right outer join. Since: JPA 2.0
3

Criteria Query From Elements

(bound by an entity class) are represented by the Root subinterface: Join variables (bound by an attribute of a preceding variable in the FROM clause) are represented by the Join subinterface and its descendant interfaces: See the FROM in Criteria Queries section for more details and examples. Join
3

javax.persistence.criteria.FetchParent

, Join, ListJoin, MapJoin, PluralJoin, Root, SetJoin Represents an element of the from clause ... a fetch join to the specified attribute using an inner join. Create a fetch join to the specified attribute using an inner join. Parameters: attributeName - name of the attribute for the target
3

Query Execution Error

JOIN $1.mitgliedschaft $2 LEFT JOIN $2.abteilungen $3 LEFT JOIN $3.abteilung $4 WHERE (((NOT ((($2 ... com.lexware.vereinsverwaltung.verein.mitglied.Mitglied $1 LEFT JOIN $1.mitgliedschaft $2 LEFT JOIN $2.abteilungen $3 LEFT JOIN $3.abteilung $4 WHERE (((NOT ((($2 IS NOT NULL) AND ($3 IS NOT NULL
3

Strings in JPQL and Criteria Queries

(_) - which matches any single character. The left operand is always the string to check

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support